5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
- Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 3-17: Using Event Points

End of Frame


The End of Frame event point executes once for a frame, immediately after the final execution of the image-level event points, before the invocation of any automatic child processes and before the frame ends. It executes for input, output and inquiry processes only.

End of Frame is often used to determine how a frame ends (END, CANCEL, PREVIOUS IMAGE, RETURN, NEXT RECORD, or ACKNOWLEDGE DELETE, for example) by interrogating the predefined field OPTION, and then performing any required action.

Immediately after End of Frame completes, APPX interrogates the INCLUDE CHILDREN predefined field to determine whether or not to skip the automatic children that are associated with the frame. If the INCLUDE CHILDREN predefined field has been preset with a value of N or 0 (no), then the associated automatic children are not executed. This field is defaulted to Y or 1 (yes) and these values are retained unless specifically changed by the designer.

Application Design Manual                                         "Powered by Appx Software"

486

©2006 By APPX Software, Inc. All Rights Reserved